@sanity @rail

Feature: Rail order and ops rail order timehseet functionalities

File name: laborOrder_rail.feature

Relative path: features/laborOrder_rail.feature

Scenarios

Chart

Status Progress

Passed	100.00 %
Failed	0.00 %

@sanity @rail

Given TR user logged into the application

Given the user creates a new Rail order

Then the user push the Rail labor order to the summary sheet

Given the user creates a new rail timesheet

When the user saves the rail order without submitting it

Then the user saves and submits the rail order

Then user click on logout button

Then Ops user logged into the application

Then Ops user submits and approve the rail order timesheet

Then ops user reject the rail timesheet

Then verify remove approval functionality in rail timehseet

Then user click on logout button

Then Timehseet entry user logged into the application

Then Labor entry add new steady details and mgr comments and submit the rail order timehseet

Then user click on logout button

Then Ops user logged into the application

Then Ops user submits and approve the rail order timesheet

Then the user verifies the download report functionality for the rail order

Then user click on logout button

After

+ Screenshot + Video